Real-time Action Objects

These Action Objects (AO) are executing configurations using real-time data sources, which are deployed online. The CSense Runtime Manager provides valuable information about the following properties:

Header

Description

PID (Process Identification)

This enables you to cross reference the identification number of the process within the Task Manager.

Server name

The name given to the AO, saved in the application creating the blueprint. The default name is the name of the file and the AO will be deployed with this name. If a name clash occurs, names will automatically be made unique. Edit the name by choosing [Deployment], highlighting the specific name, selecting [Edit] and typing in a new name. Clicking [OK] will save the changes.

Deployment

  • Starting: The indicates the time from when the AO is added and the first execution of the initialized run-time server. The duration of the starting time is determined by the complexity of the blueprint and how long it takes to be deployed.   

  • Started: The AO is executing.

  • Stopped: The AO is no longer executing. Check to see if there is an error in the real-time data source.

  • Scheduled: During service startup, some Action Objects may be scheduled to start after a delay. These will be labelled "scheduled" until deployment begins.

Status

The possible execution state of the deployed Action Objects as

 

  • UNINITIALIZED: The AO has been created, but has not been initialized yet.  

  • INITIALIZED: The AO has been created and initialized, but no blueprint has been loaded into the server yet.  

  • LOADED: An AO in this state has been created, initialized and a blueprint has been loaded successfully into the server.

  • BUILT: The AO has been created, initialized and loaded successfully. All data flows have been built at this stage.

  • RUNTIME INITIALIZED: This AO has passed its run-time initialization check.

  • RUNTIME PRE-CHECKED: This AO has passed its run-time pre-check.

  • EXECUTING: The AO has started its execution successfully.

  • FINISHED: The AO has finished its execution.

  • SHUTTING DOWN: The AO is currently shutting down.

  • ERROR: This AO has encountered an error and has stopped its execution. See the Event Viewer for more information on the nature of the error.

Execution up-time

The duration that the AO has been executing. "N/A" will be shown until the AO has started its first execution.

Last execution

The time when the AO was last executed. This column will be empty if no execution strated or the execution is delayed.

Next execution

The next time when the AO will be executed.

Overload count

This specifies how many executes are running behind, e.g. if the blueprint executes every 2 seconds, but each execute takes 5 seconds, you will see this value increase. A non-zero value here indicates that the execution rate is too fast and / or your hardware needs greater capability. Only started and stopped AOs will display a value for this property.

Execution start time

The date and time of the first AO execution. This indicates the exact time at which the AO was started, not the time the AO was created. "N/A" will be shown until the AO has started its first execution.

Resource Gauges

Resource gauges help you to understand the utilization of resources in your system. On the Real-time Action Objects window, you can view the current CPU, and Memory utilization of your system.

Understanding the Gauges

  • CPU gauge- This indicates the current utilization of your systems CPU in %. 

  • Memory gauge- This indicates the current utilization of your systems memory in %.


Related topics:

  

CSense 2023- Last updated: June 24,2025